home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
TeX 1995 July
/
TeX CD-ROM July 1995 (Disc 1)(Walnut Creek)(1995).ISO
/
tex-k
/
tex-k-archive.past
/
tex-k-archive.gz
/
tex-k-archive
/
000273_neal@ctd.comsat.com_Mon Feb 7 11:57:00 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-11
|
1KB
Received: from neal.ctd.comsat.com by cs.umb.edu with SMTP id AA16133
(5.65c/IDA-1.4.4 for <tex-k@cs.umb.edu>); Mon, 7 Feb 1994 16:57:39 -0500
Received: by neal.ctd.comsat.com (Smail3.1.28.1 #29)
id m0pTdxa-0002fOC; Mon, 7 Feb 94 16:57 EST
Message-Id: <m0pTdxa-0002fOC@neal.ctd.comsat.com>
Date: Mon, 7 Feb 94 16:57 EST
From: neal@ctd.comsat.com (Neal Becker)
To: tex-k@cs.umb.edu
Subject: kpathsea missing functionality
I have been asked to see if I can add kpathsea to the 'eps' driver I
wrote. I'd like to give this a try, but I have some problems.
eps is a driver for dot matrix printers, based on the 'mctex' library.
The problem is:
=> just because a font is 300 dpi doesn't mean it's for a CanonCX
printer.
I'm sorry if I'm sounding a little redundant, but this has to be
addressed. As far as I can tell this is not addressed in the current
implementation of kpathsea.
There has to be a way to specify that you want fonts for a particular
engine. There also has to be a way to tell kpathsea how/where to find
fonts for different engines.
I can only suggest a seperate runtime configuration file - (good thing
nobody can hit me with a tomatoe from here). This is how mctex does
it.
Any suggestions?